Fix workflows: upstream renamed facebook/react → react/react - #557

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
fa-legacy-reactjs-org	Ignored	Preview	Oct 4, 2026 12:50pm UTC

Hi maintainers! This PR is ready for review. It fixes the broken Label Core Team PRs and Discord Notify workflows (both fail on every PR with workflow was not found because they still reference facebook/react, which was renamed to react/react). Just a 2-line change — would appreciate a look. Thanks! 🙏

The check_maintainer job defines the uses key twice with different reusable workflow references. YAML does not support duplicate keys reliably, and a GitHub Actions job can reference only one reusable workflow. Please verify the intended repository and keep a single uses entry.

Thanks for the review. I re-checked the head commit (97ea57c) and there is only one uses: key per job — the diff replaces the existing value on that line, it does not add a second one:

• .github/workflows/label_core_team_prs.yml line 14 → uses: react/react/.github/workflows/shared_check_maintainer.yml@main
• .github/workflows/discord_notify.yml line 11 → same reference

The permissions: and with: blocks right below it belong to that same single job, so the YAML has no duplicate key (GitHub would reject the whole workflow file otherwise, and both files parse fine today).

I also verified the target workflow still exposes the workflow_call interface this repo consumes: react/react/.github/workflows/shared_check_maintainer.yml@main takes the actor input and returns the is_core_team output used by the if: conditions here. facebook/react and react/react resolve to the same file, but uses: does not follow the repo rename, which is why these two workflows fail on every PR with workflow was not found.

Friendly bump for the maintainers: this is a 2-line fix and both Label Core Team PRs and Discord Notify are still broken on every incoming PR. Happy to adjust anything you'd prefer. 🙏